home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
kermit.columbia.edu
/
kermit.columbia.edu.tar
/
kermit.columbia.edu
/
newsgroups
/
misc.19950329-19950528
/
000139_news@columbia.edu_Fri Apr 14 17:14:39 1995.msg
< prev
next >
Wrap
Internet Message Format
|
1995-07-31
|
2KB
Received: from apakabar.cc.columbia.edu by watsun.cc.columbia.edu with SMTP id AA22252
(5.65c+CU/IDA-1.4.4/HLK for <kermit.misc@watsun.cc.columbia.edu>); Sat, 15 Apr 1995 06:00:48 -0400
Received: by apakabar.cc.columbia.edu id AA26498
(5.65c+CU/IDA-1.4.4/HLK for kermit.misc@watsun); Sat, 15 Apr 1995 06:00:47 -0400
Path: news.columbia.edu!sol.ctr.columbia.edu!howland.reston.ans.net!swrinde!cs.utexas.edu!news.cs.utah.edu!cc.usu.edu!jrd
From: jrd@cc.usu.edu (Joe Doupnik)
Newsgroups: comp.protocols.kermit.misc
Subject: Re: Help - MSKermit, WFW 3.11 and missing COM port?
Message-Id: <1995Apr14.231439.47586@cc.usu.edu>
Date: 14 Apr 95 23:14:39 MDT
References: <3mlt7o$hh0@lucy.infi.net>
Organization: Utah State University
Lines: 21
Apparently-To: kermit.misc@watsun.cc.columbia.edu
In article <3mlt7o$hh0@lucy.infi.net>, btarr@infi.net (Bruce Tarr) writes:
> I have seen several 486 PCs with DOS 6.22, WFW 3.11 and Kermit 3.11 have
> this same problem: When Kermit is first executed after rebooting, and
> sometimes at other random times, the COM2 port is reported as not found and
> the port defaults to BIOS2. This provides very slow response times and
> sometimes hangs the machines. If you simply exit the Kermit program and
> try again, it always connects to the COM port correctly. The problem has
> never appeared under DOS. The machines have COM1 and COM2 ports and no
> other devices are using IRQ 4 or 3. Any known solutions, work arounds or
> comments will be appreciated.
----------
I'd say your COM2 port has troubles of some kind. As Frank da Cruz
says, Windows grabs the hardware and only simulates it within Windows
(to MSK). Initalizing serial ports is a fine art today with the high
varibility of port hardware on the market.
Major item to resolve is ensure there are no IRQ or Port conflicts.
After that it's between Windows and your hardware. Some internal modems
and some big square chip UARTs have difficulties after the system boots
and only very careful treatment will make them respond the first time.
So you may want to shop the net for a replacment Windows serial port driver.
Joe D.